You're waiting for client action, not server action

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

Subject:

The server-side changes happen fairly quickly - you're waiting for the client to check in and ask for updates. And if clients did that every couple of minutes, your server would not be very happy.

In a controlled environment, you can force the client to check immediately for an updated certificate table by switching ID files/locations (from ID file A to ID file B), connecting to ID file B's home server, then switching IDs back to ID file A again and connecting to ID file A's home server.

But if you're waiting for end users to do something, then the next client re-poll will occur on the next home server authentication that is more than 24 hours after the last time that the client checked for new certificates.

Here are the relevant notes.ini entries from one of my clients:

CertificateExpChecked=dkern.id 01/19/2011
RequestCertTableUpdate=dkern.id 01/19/2011

Deleting those entries from the client and re-launching would have the same effect as the switch ID dance above.

Feedback response number DKEN8D9TKJ created by ~Ben Umboosichekader on 01/19/2011